home *** CD-ROM | disk | FTP | other *** search
- Path: news.umbc.edu!not-for-mail
- From: msokos1@umbc.edu (sokos mark)
- Newsgroups: comp.sys.cbm
- Subject: Re: Using full/almost full 64k on C=64?
- Date: 29 Jan 1996 08:35:48 -0500
- Organization: University of Maryland, Baltimore County
- Message-ID: <4eiifk$phq@umbc9.umbc.edu>
- References: <s10c7c09.061@shands.ufl.edu>
- NNTP-Posting-Host: umbc9.umbc.edu
- NNTP-Posting-User: msokos1
-
- In article <s10c7c09.061@shands.ufl.edu>, <mello.med@shands.ufl.edu> wrote:
- >The C= programmers reference guide is vague on the procedures for
- >using all of the 64k for programming. I have several questions
- >if someone would like to take a crack at them for me?
- >
- >If you wanted to use more than the 38911 or whatever it is
- >available for programs, how do you do it?
-
- There are several things you can do. You can turn off the ROMs and
- use the RAM mapped beneath them. Your program will have to be in
- assembly, so it doesn't depend on the basic interpreter in one of
- the rom chips. You can also hide code under the roms, then swap
- out that code or data to another area of memory when needed. You
- can also have your program load and execute code from a disk. You
- can get very large programs this way, but the disk access is SLOW.
-
- >What I/O routines would have to be coded if you are using the
- >full 64k?
-
- If you are turning off the ROMs, you need to code any routine that
- is in them, or alternately, you just turn them back on when you need
- any of the i/o routines in them, then turn them back off when you
- are done.
-
- - Mark Sokos (msokos1@gl.umbc.edu)
- Electrical engineer, computer geek (er, programmer) in training,
- no-talent bum musician (have bass, will travel), and perpetual student
-